Flexible profile grouping download

ABSTRACT

A method for providing of data is provided, the method comprising at a first database: providing of group data; providing of data of a first entity, in particular of a first device, the data of the first entity comprising the group data; receiving from a second database a request for the data of the first entity; determining that the data of the first entity comprises the group data and that said group data has not been sent to the second database before; and if said determining step is in the affirmative, sending the data of the first entity comprising the group data to the second database.

TECHNICAL FIELD

The invention relates to databases and methods for providing data. Inparticular, the invention relates to databases and methods enablingflexible profile grouping download. Furthermore, the invention relatesto a system, program elements and a computer-readable medium.

BACKGROUND

In the field of data communication or providing data, in particular inmobile networks, different ways for handling or providing great amountsof data or to provide the same data to different devices are known. Theprovision of data includes transferring of data from one device toanother device. In order to reduce the amount of data to be transferredor communicated to provide a given amount of payload data to the devicesseveral ways like grouping of the devices are known.

For example so called Machine Type Communication (MTC) Groups are known.MTC applications generally involve a group of devices. Typicallyapplications today involve more than 1000 subscriptions for a singlecustomer. From both customer and operator points of view, there isbenefit in optimised handling of groups of MTC devices.

One possibility belongs to 3^(rd) Generation Partnership Project (3GPP)MTC, see for example 3GPP TR 23.887 v0.5.0 dated 28 Nov. 2012. Inparticular, 3GPP SA2 is studying different solutions to optimize thenetwork by grouping devices for the following key issues:

Group based Messaging: to efficiently distribute the same message (e.g.a trigger request) to those members of an MTC group that are located ina particular geographical area on request of the Service CapabilityServer (SCS).

Group based Charging: In many cases, the data volume of CDRs generatedby MTC applications is greater than the volume of actual user datatransmitted. In these cases it may be beneficial to create bulk CDRs tocount chargeable events per group instead of CDR creation per individualdevice.

Group based Policing: to enforce a policy for a group of MTC devices.This allows greater flexibility to the MTC application or MTCapplication owner compared to individual policies for each of thedevices, while at the same time ensuring the operator that theparticular group of MTC devices does not unduly load the network.

Group based identifying and addressing: essential to support group basedfeatures such as messaging, charging and policing.

Furthermore Profile Grouping is known. In particular, there will begroups of MTC devices that will typically have subscribed the sameservice profile or at least a common set of services.

However, several problems are linked with existing solutions. One of themost challenging issues for companies operating cellular networks is theoverload of its networks due to the drastic increase of signaling due toMTC devices. Besides, the ratio between network signaling (that isusually not billed) and network payload (that can be billed) coulddecrease a lot for certain types of devices.

Profile grouping in central databases can optimize provisioning andstorage resources in the central database, but when populating suchprofiles to other local databases in the network will mean massiveprocedures.

For example, all of a group of fire alarms spread in a wood connected tothe central alarm system through a GPRSLTE wireless connection may havethe same 3GPP data profile. All of them are connected to the sameSGSNMME. When these 2000 devices are attached, 2000 Location Updatingare needed where the same profile is downloaded 2000 times. Besides, ifafter sometime the profile changes for the whole group (for example thealarm system decides to change the power saving profile due to a heatwave) 2000 thousand messages need to be sent to the same SGSNMME withthe same data change.

SUMMARY

It is an object of the invention to provide databases and methods forproviding data which at least overcome some of the above mentionedproblems.

In order to achieve the object defined above, a database, a method forproviding data, a system, program elements and a computer readablemedium according to the independent claims are provided.

According to an exemplary aspect a method for providing of data isprovided, the method comprising at a first database: providing of groupdata; providing of data of a first entity, in particular of a firstdevice, the data of the first entity comprising the group data;receiving from a second database a request for the data of the firstentity; determining that the data of the first entity comprises thegroup data and that said group data has not been sent to the seconddatabase before; and if said determining step is in the affirmative,sending the data of the first entity comprising the group data to thesecond database.

In particular, the first database may be a central database, e.g. a HomeSubscriber Server (HSS). For example, the group data may be providedfrom a provisioning system or stored by any other means at the firstdatabase. In particular, the data for the first entity, e.g. a firstdevice, a first subscriber or a first subscription, may be provided froma provisioning system or stored by any other means at the firstdatabase. In general, the term entity may particular refer to a device,a subscriber, a subscription, or the like. For example, the seconddatabase may be a local database such as Mobile Switching Center (MSC),or Serving GPRS Support Node (SGSN), Mobile Management Entity (MME), orthe like.

According to an exemplary aspect a method for providing of data, themethod comprising at a second database: sending to a first database arequest for data of a first entity; receiving from the first databasethe data of the first entity comprising group data; storing the data ofthe first entity comprising the group data: sending to the firstdatabase a request for data of a second entity; receiving from the firstdatabase the data of the second entity without the group data; andstoring the data of the second entity comprising the group data asobtained from the received data of the first entity.

In particular, the second database may be a local database such as MSCor SGSN or MME or the like, while the first database may be a centraldatabase such as an HSS or the like. For example, the request for dataof a first entity might be triggered by reception of a first serviceaccess for a first entity, e.g. a first device, subscriber, subscriptionor the like, at the second database. In particular, the group data maybe contained in a stored data set or linked to it, the latter may beuseful if the group data has a large size. For example, the request fordata of a second entity, e.g. device, subscriber, subscription or thelike, might be triggered by reception of a second service access for asecond entity at the second database. In particular, the group data maybe contained in a stored data set or linked to it, the latter beinguseful if the group data has a large size.

According to an exemplary aspect a first database is provided which isadapted to perform the method according to an exemplary aspect.

According to an exemplary aspect a first database is provided whereinthe first database comprises a receiving unit, a transmission unit, aprocessing unit, and a storage unit, wherein the storage unit is adaptedto store group data and data of a first entity, in particular a firstdevice, the data of the first entity comprising the group data; whereinthe receiving unit is adapted to receive from a second database arequest for the data of the first entity; and wherein the processingunit is adapted to determine that the data of the first entity comprisesthe group data and that said group data has not been sent to the seconddatabase before and if said determining step is in the affirmative beingadapted to initiate a sending via the transmission unit of the data ofthe first entity comprising the group data to the second database.

According to an exemplary aspect a second database is provided which isadapted to perform the method according to an exemplary aspect.

According to an exemplary aspect a second database is provided whereinthe second database comprises a receiving unit, a transmission unit, aprocessing unit, and a storage unit, wherein the transmission unit isadapted to send to a first database a request for data of a firstentity, in particular of a first device; the receiving unit is adaptedto receive from the first database the data of the first entitycomprising group data; the storage unit is adapted to store the data ofthe first entity comprising the group data; the transmission unit isadapted to send to the first database a request for data of a secondentity, in particular a second device; the receiving unit is adapted toreceive from the first database the data of the second entity withoutthe group data; and the storage unit is adapted to store the data of thesecond entity comprising the group data as obtained from the receiveddata of the first entity.

In particular, the group data may be obtained by the processing unit.For example, the group data may be contained in a stored data set orlinked to it, the latter being useful if the group data has a largesize.

According to an exemplary aspect a system, in particular a system for a(mobile) communication network, is provided wherein the system comprisesa first database according to an exemplary aspect and a second databaseaccording to an exemplary aspect.

According to another exemplary aspect, a program element (for instance asoftware routine, in source code or in executable code) is provided,which, when being executed by a processor, is adapted to control orcarry out a method according to an exemplary aspect having the abovementioned features.

According to yet another exemplary aspect, a computer-readable medium(for instance a CD, a DVD, a USB stick, a floppy disk or a hard disk) isprovided, in which a computer program is stored which, when beingexecuted by a processor, is adapted to control or carry out a methodaccording to an exemplary aspect having the above mentioned features.

A gist of an exemplary aspect may relate to a mechanism adapted topopulate device data profiles in a network in an efficient manner bygrouping such data profiles. The mechanism may permit that the profilegrouping is flexible so local databases do not need to be pre-configuredwith predefined group data, but this data may be defined flexibly (e.g.not pre-agreed or standardized) and it may be dynamically configured inthe local databases when it is needed. Alternatively or in addition, itmay be possible that group data, e.g. data relating or associated withall entities of one group or to the configuration of the entities of onegroup, may only be sent once so that the amount of data to betransferred may be reduced.

The aspects defined above and further aspects are apparent from theexamples of embodiment to be described hereinafter and are explainedwith reference to these examples of embodiment.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, embodiments of the invention are described in moredetail hereinafter with reference to examples but to which the scope isnot limited.

FIG. 1 schematically illustrates of a system according to an exemplaryembodiment.

FIG. 2 schematically illustrates a method for device data download to aserving node.

FIG. 3 schematically illustrates an updating of group data.

FIG. 4 schematically illustrates a deleting of group data from localdatabase.

FIG. 5 schematically illustrates an embodiment referring to a 3GPPmobility management use case.

FIG. 6 schematically illustrates an embodiment of updating group dataGPRSLTE.

FIG. 7 schematically illustrate a flowchart for a method according to anexemplary embodiment performed at a first or central database.

FIG. 8 schematically illustrate a flowchart for a method according to anexemplary embodiment performed at a second or local database.

DETAILED DESCRIPTION

In the context of this application, the term “group data” mayparticularly denote data which is common to a group and/orcharacterizing a group, e.g. a group of devices, subscriber,subscription or the like.

The term “identifier” may particularly denote data or informationidentifying or defining a specific entity and/or characteristic of anentity. For example, an identifier may identify the belonging to a groupdenoted e.g. as “group A”. In particular, such an identifier may be usedto identify the belonging of a specific entity to a specific group.

The term “entity” may particularly denote any entity, node, element, oreven person being part, user, or provider, or the like of acommunication network. For example, an entity may be a device, asubscriber or subscription. The terminology data of an entity or entitydata may refer to data of a device (e.g. of a first or second device orgroup data comprised in device data). However, this does not excludethat the data of an entity can be equivalently regarded as related to asubscription or a subscriber. Hence, data of a device or a subscriber ora subscription can be equivalently used to identify or relate data to anentity in a communication system, the entity being e.g. a device, asubscriber, or a subscription. So, “device data” or “data of a device”in the examples and embodiments herein might be generalized by “entitydata” or “data of an entity”. In that sense “group data common to agroup of devices” might be “group data common to a group of entities”and “device-specific data” might be “entity-specific data”.

In the following, with referring to FIGS. 7 and 8, the principle stepsof two methods according to exemplary aspects are described. It shouldbe noted that the steps described in the context of FIGS. 7 and 8 arenot necessarily performed in the described order but may be shifted.

In particular, FIG. 7 describes a method which may be performed by afirst database of a system, e.g. a system for a (mobile) communicationnetwork.

In a first step (step 700), group data are provided and optionallystored at the first database, e.g. a central database. Additionally,data of a first entity, e.g. of a first device, are provided andpreferably stored at the first database, wherein the data of the firstentity comprises the group data (step 701). In the following, the firstdatabase receives a request for the data of the first entity from asecond database, e.g. a local database (step 702). Upon the request thefirst database determines whether/that the data of the first entitycomprises the group data and that said group data has not sent to thesecond database (step 703). In case the determining step is positive oraffirmative the data of the first entity which comprises the group datais sent to the second database (step 704).

In particular, FIG. 8 describes a method which may be performed by asecond database, e.g. a local database, of a system, e.g. a system for a(mobile) communication network.

In a first step (step 800), the second database sends a request for dataof a first entity to a first database, e.g. a central database.Thereupon the second database receives from the first database the dataof the first entity, which data comprises group data (step 801). Thenthe second database stores the received data of the first entity whichdata comprises the group data (step 802). Afterwards the second databasesends a request for data of a second entity to the first database (step803), whereupon the second database receives the data of the secondentity without the group data from the database (step 804). Then thesecond database stores the data of the second entity comprising thegroup data as obtained from the received data of the first entity (step805)

A method according to the embodiments described in the context of FIG. 7and FIG. 8 may enable a mechanism adapted to populate device dataprofiles in a network in an efficient manner by grouping such dataprofiles which may enable a flexible grouping where local databases donot need to be pre-configured with predefined group data.

A first database, e.g. a central database, where entity data, e.g.device data, may be permanently stored is provisioned with group datacorresponding to a group of entities, e.g. devices, and with individualdata for such entities, e.g. devices.

When a second database, e.g. a local database, temporally needs profiledata for one entity, e.g. a device, the central database can downloadthe whole profile data for such entity, e.g. a device, both the profiledata corresponding to the group the entity, e.g. device, belongs to andindividual data if any. The second or local database can now bepopulated with the profile data for this group, apart from theindividual entity data.

Next time that this second or local database needs profile data foranother entity, e.g. device, of the same group, the first or centraldatabase can recognize that the “another entity (e.g. device)” belongsto the same group as the “one entity (device)” mentioned above belongsto. As a consequence, only the group identity may be downloaded to saidsecond or local database (to indicate the belonging of the “anotherentity (e.g. device)” to the same group as for the “one entity (e.g.device)” such that the second or local database is able to use the groupprofile data downloaded for the “one entity (e.g. device)” also for the“another entity (e.g. device)”), together with individual data specificfor such entity, e.g. device) if any. So, group data does not need to bedownloaded again.

If any group data is changed later on, there is no need for massiveupdate of local databases, only one message per local data base may beneeded to inform about the change.

This may be a great save of signaling resources when grouping highamount of entities, e.g. devices, with the same or similar profile datathat access the same serving node. In particular, the databases andmethods may facilitate efficient provision of data, for example of amobile network.

Next, further exemplary embodiments of the methods for providing of dataare described. However, these embodiments also apply to a local orsecond database, to a central or first database, a system, programelements, and to a computer readable medium.

According to an exemplary embodiment the method further comprisesproviding of data of a second entity, in particular of a second device,the data of the second entity comprising the group data; receiving fromthe second database a request for the data of the second entity;determining that the data of the second entity comprises the group dataand that said group data has been sent to the second database before;and if said determining step is in the affirmative, sending the data ofthe second entity without the group data to the second database.

In particular, the data for the second entity, e.g. a second device, asecond subscriber or a second subscription, may be provided from aprovisioning system or stored by any other means at the first database.For example, the second database may be a local database such as MSC orSGSN or MME or the like.

According to an exemplary embodiment of the method the group data isidentified by a group data identifier and said sending of the data ofthe second entity without the group data to the second databasecomprises the group data identifier.

The usage of a group data identifier for identifying the belonging ofspecific data and/or entity to a specific group may provide an efficientway, in particular a way needing only a small amount of data, to definegroups.

According to an exemplary embodiment of the method said sending of thedata of the first entity comprising the group data to the seconddatabase comprises the group data identifier.

According to an exemplary embodiment the method further comprisesreceiving, at the first database, an indication of a no-usage of thegroup data at the second database; and sending, in response to saidreception of said indication, to the second database an instruction todelete the group data from the second database.

The sending and/or receiving of a no-usage message or indication may bean efficient way to inform another entity or network element, e.g. afurther database, of the fact that specific data are not used anymore,so that the respective specific data may be deleted, therefore possiblyreducing the necessary storage space.

According to an exemplary embodiment the method further comprisesreceiving, from the second database, an indication indicative for adeletion of the group data in the second database.

In particular, the first database may receive a specific messageincluding the indication indicative of the deletion of the group data,wherein the message may be sent by the first database, for example. Thesending and/or receiving of a deletion indication message may be usefulfor avoiding or at least reducing the frequency of sending group dataupdates to secondary or second databases which already deleted therespective group data or where this group data are not present anymore.

According to an exemplary embodiment of the method the first databasekeeps a list of second databases which provide said group data.

In particular, the list may be updated when the first database receives,e.g. from the second database, the indication indicative for a deletionof the group data in the second database. For example, such a list maybe kept at the first database in the form of a table or a flagsassociated with the respective second databases. In particular, a flagassociated with a second database may be set at the first databasewherein the flag is indicative that the second database stores saidgroup data. Alternatively, the list of second databases or serving nodesmay be updated by deleting the second databases from the list of seconddatabases when the first database is informed that no entity of thegroup is stored on said second database anymore.

According to an exemplary embodiment the method further comprisessending the updated group data to the second databases on the list.

In particular, the first database may firstly determine whether saidgroup data has been updated. After it is determined that the group datahas been updated the group data may only be sent to databases on thelist. For example, the group data may only be sent to the seconddatabases or serving nodes labeled or associated with a flag statusindicative that the specific database still stores said group data.Thus, it may be possible to avoid that updated group data are sent todatabases which does not store the respective group data. Therefore theamount of sent data may be reduced.

According to an exemplary embodiment of the method the group data isidentified by a group data identifier and said receiving of the data ofthe first entity comprises the group data identifier and said receivingof the data of the second entity comprises the group data identifier.

In particular, the group data identifier identifies the belonging to agroup, e.g. a group denoted as “group A”.

According to an exemplary embodiment of the method the group data isobtained from the received data of the first entity based on adetermination of the group data identifier comprised in the data of thefirst entity being the same as the group data identifier comprised inthe data of the second entity.

As an example, when the second database recognizes (determines) that thegroup data identifiers of the data of the first entity and the secondentity, e.g. device, subscriber or subscription, are the same, itrecognizes (determines) that the group data of the first entity can beused also for the data of the second entity and can process accordinglyto store the group data also for the data of the second entity.

According to an exemplary embodiment the method further comprisesreceiving an update of the group data; replacing the group data storedin the data of the first entity with the updated group data; andreplacing the group data stored in the data of the second entity withthe updated group data.

According to an exemplary embodiment the method further comprisesdetermining no-usage for any of the data of the first entity and thesecond entity.

In particular, no-usage may be determined when the last device from thegroup is deleted from the second database. For example, no-usage may beno current and/or no future use. The no-usage may be determined by anysuitable entity, e.g. the first database or the second database.

According to an exemplary embodiment the method further comprises ifsaid determination of no-usage is in the affirmative, deleting the groupdata from the second database.

According to an exemplary embodiment the method further comprisessending an indication of the deletion to the first database.

In particular, such a sending of an indication may help to keep thedatabases on the same status. For example, the second database may sendthe indication to the first database, which then may delete the data aswell or keep the data. However, in any case the first database does atleast know that the respective deletion was performed at the seconddatabase.

According to an exemplary embodiment the method further comprises ifsaid determination of no-usage is in the affirmative, sending anindication of the no-usage of the group data to the first database.

According to an exemplary embodiment the method further comprisesreceiving, in response to said sending of said indication, from thefirst database an instruction to delete the group data from the seconddatabase; and deleting the group data from the second database.

In general, the data of an entity, e.g. of an device, might beidentified at the first database and/or the second database by an entity(e.g. device) data identifier, e.g. a first entity identifier might beassociated to the data of the first entity and a second entityidentifier to the data of the second entity. The first and second entitydata identifier might be comprised in the request for the data of thefirst and second entity, respectively. The data of the first and thesecond entity comprises the group data. In addition it might comprisefurther entity specific data (e.g. denoted as D1indivData or “firstdevice individual data” and D2indivData, as in the following describedin the context of FIG. 2 or 5, or “second device individual data” forthe first entity and the second entity, respectively, in some examples).

In that regard the sending of the data of the second entity without thegroup data might contain second entity specific data (e.g. denoted asD2indivData in some examples) or not, i.e. in the latter case thesending of the data of the second entity does not carry any device datawith respect to the second entity at all. The sending might be in thiscase a response message to the earlier request with the response messagecarrying an empty data field for the data of the second entity.

Next, further exemplary embodiments of the first database, e.g. a globaldatabase or central database, are described. However, these embodimentsalso apply to the method for providing of data, the local or seconddatabase, the system, program elements, and to a computer readablemedium.

According to an exemplary embodiment of the first database the storageunit is adapted to store data of a second entity, in particular a seconddevice, the data of the second entity comprising the group data; thereceiving unit is adapted to receive from the second database a requestfor the data of the second entity; and the processing unit is adapted todetermine that the data of the second entity comprises the group dataand that said group data has been sent to the second database before andif said determining step is in the affirmative, to initiate a sendingvia the transmission unit of the data of the second entity without thegroup data to the second database

According to an exemplary embodiment of the first database the groupdata is identified by a group data identifier and said sending of thedata of the second entity without the group data to the second databasecomprises the group data identifier.

According to an exemplary embodiment of the first database said sendingof the data of the first entity comprising the group data to the seconddatabase comprises the group data identifier.

According to an exemplary embodiment of the first database the receivingunit being adapted to receive an indication of a no-usage of the groupdata at the second database and the transmission unit being adapted tosend, in response to said reception of said indication, to the seconddatabase an instruction to delete the group data from the seconddatabase.

According to an exemplary embodiment of the first database the receivingunit being adapted to receive, from the second database, an indicationindicative for a deletion of the group data in the second database.

According to an exemplary embodiment of the first database the firstdatabase being adapted to keep a list of second databases which providesaid group data.

According to an exemplary embodiment of the first database thetransmission unit being adapted to send the updated group data to thesecond databases on the list.

Next, further exemplary embodiments of the second database, e.g. a localdatabase, are described. However, these embodiments also apply to themethod for providing of data, the global or first database, the system,program elements, and to a computer readable medium.

According to an exemplary embodiment of the second database the groupdata is identified by a group data identifier and said receiving of thedata of the first entity comprises the group data identifier and saidreceiving of the data of the second entity comprises the group dataidentifier.

In particular, the group data identifier identifies the belonging to agroup, e.g. a group denoted as “group A”.

According to an exemplary embodiment of the second database theprocessing unit is adapted to obtain the group data from the receiveddata of the first entity based on a determination of the group dataidentifier comprised in the data of the first entity being the same asthe group data identifier comprised in the data of the second entity.

As an example, when the processing unit of the second databaserecognizes (determines) that the group data identifiers of the data ofthe first and the second entity are the same, it recognizes (determines)that the group data of the first entity can be used also for the data ofthe second entity and can process accordingly to store the group dataalso for the data of the second entity.

According to an exemplary embodiment of the second database thereceiving unit is adapted to receive an update of the group data; theprocessing unit is adapted to replace the group data stored in the dataof the first entity with the updated group data; and the processing unitis adapted to replace the group data stored in the data of the secondentity with the updated group data.

According to an exemplary embodiment of the second database theprocessing unit is adapted to determine no-usage for any of the data ofthe first and the second entity.

According to an exemplary embodiment of the second database if saiddetermination of no-usage is in the affirmative, the processing unit isadapted to delete the group data from the storage unit of seconddatabase.

According to an exemplary embodiment of the second database thetransmission unit is adapted to send an indication of the deletion tothe first database.

According to an exemplary embodiment of the second database if saiddetermination of no-usage is in the affirmative, the transmission unitis adapted to send an indication of the no-usage of the group data tothe first database.

According to an exemplary embodiment of the second database thereceiving unit is adapted to receive, in response to said sending ofsaid indication, from the first database an instruction to delete thegroup data from the second database, and the processing unit is adaptedto delete the group data from the storage unit of the second database.

At least some of the above described databases and methods may provide agreat save of signaling resources when grouping high amount of entities,e.g. devices, with the same or similar profile data that access the sameserving node. In particular, the databases and methods may facilitateefficient provision of data, for example of a mobile network.

In the following some principles of the databases and the methodsaccording to exemplary embodiments are described while referring to thedrawings.

FIG. 1 schematically illustrates a system 110 comprising a firstdatabase 100 which may be a central database and a second database 102which may be a local database.

The first database 100 comprises a first receiving unit R1 which isadapted to receive communication messages, like requests. The firstreceiving unit R1 is coupled to a first processing unit P1 which is inturn coupled to a first storage unit S1. Furthermore, the firstprocessing unit P1 is coupled to a first transmission unit T1 which isadapted to transmit or send communication messages.

The second database 102 comprises a second receiving unit R2 which isadapted to receive communication messages, like requests. The secondreceiving unit R2 is coupled to a second processing unit P2 which is inturn coupled to a first storage unit S2. Furthermore, the firstprocessing unit P2 is coupled to a first transmission unit T2 which isadapted to transmit or send communication messages.

FIG. 2 schematically illustrates a method for device data download to aserving node. In particular, FIG. 2 illustrates an embodiment referringto a (general) message flow, e.g. in a communication network 210comprising a provisioning system 211, a central database 212, a servingnode or local database 213, a first device 214, e.g. a mobile device(also denoted as “Device1” or “M2M” (Machine-to-Machine)), and a seconddevice 215, e.g. a second mobile device (also denoted as “Device2” or“M2M” (Machine-to-Machine)). The first and second devices may be amobile phone, laptop, PDA or the like.

In a first step (step 200.A) group A data, i.e. data relating to a firstgroup A, is configured in central database. It is not needed toconfigure it in the local databases.

In next steps (step 200.B and step 200.B′) profile data is provisionedin the central database for the first device 214 and the second device215. Each of the provisioning 200.B and 200.B′ could be in one step orin more than one step, e.g. via several messages “200.B Device 1 dataprovisioning” and “200.B′ Device 2 data provisioning” as e.g. depictedin FIG. 2. They are included in group A and individual data (if any) isadded to each individual profile.

Thereafter, (step 201.) the first device 214 access a service (e.g. inthe serving node) which needs profile data of the first device from itslocal database 213.

Then, (step 202.) the local database 213 requests profile data of thefirst device 214 to the central database 212. For example, initializinga read in the central database 212 or requesting for data of the firstdevice 214.

In a next step (step 203.) the central database realizes that the firstdevice 214 belongs to group A and that the requesting local database hasnot been populated with group A data before. Then, the central databasedownloads the group A data together with individual data (if any) of thefirst device 214 to the local database 213, that stores it.

Thereafter, (step 204.) the second device 215 may access a service (inthe serving node) which needs profile data from its local database 213.

Then, (step 205.) the local database 213 requests profile data of thesecond device 215 to the central database 212. For example, initializinga read in the central database 212 or requesting for data of the seconddevice 215.

In a following step (step 206.) the central database 212 realizes thatthe second device belongs to group A, i.e. the same group as the firstdevice, and that this local database 213 has already been populated withgroup A data before. Then, the central database 212 downloads onlyindividual data (if any) of the second device to the serving node 213together with the set to group A for the device.

FIG. 3 schematically illustrates group data change population. Inparticular, FIG. 3 explains some principles of an embodiment of updatinggroup data. For example, in case the provisioning system 211 would liketo update group A data it may send a request for change of MTC group Adata to the central database 212 (step 301.), so that the group A datais changed in central database 212. Afterwards (step 302.) group datachange is sent to the local databases 213 where any device of this groupis located. In particular, the data for all entities, e.g. devices,belonging to the same group are changed or updated. If there is a highamount of devices served by the same local database 213, there is asubstantial saving of signaling.

FIG. 4 schematically illustrates a deleting of group data from localdatabase. Once the group data is stored in the local data base, it canbe decided to permanent store it there or maybe there is a need todelete it when local data base do not need it any more (individualdevice data is deleted) and it needs storage space.

Two solutions are possible according to exemplary embodiments:

-   -   Group data is deleted from local database when last device from        this group is deleted from said local database. So, when any        data of the group changes in central database, this local        database does not need to be informed.    -   Group data may be maintained after data from the last device        from this group is deleted from local database. Then, the        central database has to maintain updated the local databases        with group information although there are no individuals from        that group. The group data could be deleted later on if needed        (e.g. data storage capacity needed) and the central database        informed.

In the following principle steps of deleting of group data according tothe first alternative is described. In a first step (step 401.) thelocal database 213 decides to delete data of the first device 214 as itdoes not needed any more. The first device 214 is the last group Amember on this local database 213. In the following (step 402.) thelocal database 213 informs the central database 212 that data of thefirst device 214 has been deleted and if associated group A data hasbeen deleted or not. For example, this may be performed by a no-usagemessage, indicated that the group A data has not been used for apredetermined time-span, for example. Afterwards (step 403.) centraldatabase updates its registers accordingly.

FIG. 5 schematically illustrates an embodiment referring to a 3GPPmobility management use case. In particular, FIG. 5 shows data downloadat an attach procedure in CSGPRSLTE access network, e.g. when a locationupdate is performed. In this embodiment, an HSS 512 serves as an examplefor a central database and a MSC or SGSN or MME 513 serve as examplesfor a local database.

In the beginning (step 500.A) group A data is configured in HSS 512. Itis not needed to configure it in the serving nodes (MSCSGSNMME 513).

In the following (steps 500.B and 500B′) profile data is provisioned inthe HSS 512, for the first device 214 and the second device 215,respectively. Each of the provisioning steps 500.B and 500.B′ could bein one step or in more than one step, e.g. via several messages “500.BDevice 1 data provisioning” and “500.B′ Device 2 data provisioning” ase.g. depicted in FIG. 2. They are included in group A and individualdata (if any) is added to each individual profile.

Afterwards (step 501.) the first device 214 access a service in theMSCSGSNMME 513 which needs profile data of the first device 214.

In a next step (step 502.) the serving node request profile data of thefirst device 214 to the HSS 512 during location updating procedure.

In the following (step 503.) the HSS 512 realizes that the first device214 belongs to group A and that MSCSGSNMME 513 has not been populatedwith group A data before. Then, the HSS 512 downloads the group A datatogether with individual data (if any) of the first device 214 to theMSCSGSNMME 513, and stores it.

In a next step (step 504.) the second device 215 accesses a service inthe MSCSGSNMME 513 which needs profile data of second device 215.

Afterwards (step 505.) the MSCSGSNMME 513 requests profile data of thesecond device 215 to HSS 512 during location updating procedure.

In the following (step 506.), the HSS 512 realizes that the seconddevice 215 belongs to group A and that this MSCSGSNMME 513 has alreadybeen populated with group A data before. Then, the HSS downloads onlyindividual data (if any) of the second device 215 to the MSCSGSNMME 513together with the set to group A for the device.

FIG. 6 schematically illustrates an embodiment of updating group dataGPRSLTE. In particular, FIG. 6 schematically illustrates group insertsubscriber data. In a first step (step 601.) group A data is changed inHSS 512. Afterwards (step 602.) the HSS 512 sends one insert subscriberdata to the MSCSGSNMME 513 where any device of this group is located. Ifthere is a high amount of devices served by the same node, there is asubstantial saving of signaling.

According to another exemplary embodiment a purging of group data can beperformed. In such a purge group data embodiment the serving nodeinforms the HSS by means of a purge message when it decides to deletesubscriber data. If the serving node also deletes the correspondinggroup data (e.g. the last device from the group is deleted) the HSS isalso informed. This can be done in the same message, for example.

If the group data is not deleted in this moment but it is decided to bedeleted later on (e.g. storage capacity is needed), when no devices ofthe group are stored in this serving node, then the HSS shall also beinformed, e.g. by means of a group-purge message, so the HSS can updatethe list of serving nodes with such group data provided. So, when datagroup change in HSS, this serving node does not need to be informed.

Other examples of central/local databases where this invention could beapplied are:

-   -   HSS as central IP Multimedia Subsystem (IMS) database and        Serving Call State Control Functions (S-CSCFs) as local        databases.    -   Centralized User Database (CUDB) and Front Ends (FEs) in layer        architecture.

Beside the above described the further embodiments may be provided inwhich the methods and/or databases are further adapted to establish amechanism to solve prevalence and interactions between individual andgroup data:

-   -   Preferably, the central database sends data to local databases        so there are no interactions/inconsistencies between them.    -   If this is not possible, it is indicated at data download if        individual data has preference over group data or vice versa.    -   If the device forms part of several groups, the central database        indicates the prevalence of one group to the other for the whole        set of data or one by one.

Furthermore, it should be mentioned that all described embodimentsdescribed in this application can be combined. Thus, groupprofile/individual profile interaction embodiments may be combined.

The invention may be applied in a Global System for MobileCommunications (GSM), General Packet Radio Service (GPRS), UniversalMobile Telecommunications System (UMTS), Long Term Evolution (LTE) orany future (5G=5^(th) generation) mobile communication system orcombinations thereof. It might be further applied, alternatively or inaddition, in wired communication systems.

It should be noted that the term “comprising” does not exclude otherelements or features and the “a” or “an” does not exclude a plurality.Also elements described in association with different embodiments may becombined. It should also be noted that reference signs in the claimsshall not be construed as limiting the scope of the claims.

1. A method for providing of data, the method comprising at a firstdatabase: providing of group data; providing of data of a first entity,the data of the first entity comprising the group data; receiving from asecond database a request for the data of the first entity; determiningthat the data of the first entity comprises the group data and that saidgroup data has not been sent to the second database before; and if saiddetermining step is in the affirmative, sending the data of the firstentity comprising the group data to the second database.
 2. The methodaccording to claim 1, wherein the method further comprises: providing ofdata of a second entity the data of the second entity comprising thegroup data; receiving from the second database a request for the data ofthe second entity; determining that the data of the second entitycomprises the group data and that said group data has been sent to thesecond database before; and if said determining step is in theaffirmative, sending the data of the second entity without the groupdata to the second database.
 3. The method according to claim 2, whereinthe group data is identified by a group data identifier and said sendingof the data of the second entity without the group data to the seconddatabase comprises the group data identifier.
 4. The method according toclaim 3, wherein said sending of the data of the first entity comprisingthe group data to the second database comprises the group dataidentifier.
 5. The method according to claim 1, further comprising:receiving, at the first database, an indication of a no-usage of thegroup data at the second database; and sending, in response to saidreception of said indication, to the second database an instruction todelete the group data from the second database.
 6. The method accordingto claim 1, further comprising: receiving, from the second database, anindication indicative for a deletion of the group data in the seconddatabase.
 7. The method according to claim 1, wherein the first databasekeeps a list of second databases which provide said group data.
 8. Themethod according to claim 7, further comprising: sending the updatedgroup data to the second databases on the list.
 9. A method forproviding of data, the method comprising at a second database: sendingto a first database a request for data of a first entity; receiving fromthe first database the data of the first entity comprising group data;storing the data of the first entity comprising the group data, sendingto the first database a request for data of a second entity; receivingfrom the first database the data of the second entity without the groupdata; and storing the data of the second entity comprising the groupdata as obtained from the received data of the first entity.
 10. Themethod according to claim 9, wherein the group data is identified by agroup data identifier and said receiving of the data of the first entitycomprises the group data identifier and said receiving of the data ofthe second entity comprises the group data identifier.
 11. The methodaccording to claim 10, wherein the group data is obtained from thereceived data of the first entity based on a determination of the groupdata identifier comprised in the data of the first entity being the sameas the group data identifier comprised in the data of the second entity.12. The method according to claim 9, further comprising: receiving anupdate of the group data; replacing the group data stored in the data ofthe first entity with the updated group data; and replacing the groupdata stored in the data of the second entity with the updated groupdata.
 13. The method according to claim 9, further comprising:determining no-usage for any of the data of the first and the secondentity.
 14. The method according to claim 13, further comprising: ifsaid determination of no-usage is in the affirmative, deleting the groupdata from the second database.
 15. The method according to claim 14,further comprising: sending an indication of the deletion to the firstdatabase.
 16. The method according to claim 13, further comprising: ifsaid determination of no-usage is in the affirmative, sending anindication of the no-usage of the group data to the that database. 17.The method according to claim 16, further comprising: receiving, inresponse to said sending of said indication, from the first database aninstruction to delete the group data from the second database; anddeleting the group data from the second database.
 18. (canceled)
 19. Afirst database comprising a receiving unit, a transmission unit, aprocessing unit, and a storage unit, wherein: the storage unit isadapted to store group data and data of a first entity the data of thefirst entity comprising the group data; the receiving unit is adapted toreceive from a second database a request for the data of the firstentity; and the processing unit is adapted to determine that the data ofthe first entity comprises the group data and that said group data hasnot been sent to the second database before and if said determining stepis in the affirmative being adapted to initiate a sending via thetransmission unit of the data of the first entity comprising the groupdata to the second database.
 20. The First database according to claim19, wherein: the storage unit is adapted to store data of a secondentity the data of the second entity comprising the group data; thereceiving unit is adapted to receive from the second database a requestfor the data of the second entity; and the processing unit is adapted todetermine that the data of the second entity comprises the group dataand that said group data has been sent to the second database before andif said determining step is in the affirmative, to initiate a sendingvia the transmission unit of the data of the second entity without thegroup data to the second database. 21.-27. (canceled)
 28. A seconddatabase comprising a receiving unit, a transmission unit, a processingunit, and a storage unit, wherein: the transmission unit is adapted tosend to a first database a request for data of a first entity; thereceiving unit is adapted to receive from the first database the data ofthe first entity comprising group data; the storage unit is adapted tostore the data of the first entity comprising the group data; thetransmission unit is adapted to send to the first database a request fordata of a second entity; the receiving unit is adapted to receive fromthe first database the data of the second entity without the group data;and the storage unit is adapted to store the data of the second entitycomprising the group data as obtained from the received data of thefirst entity. 29.-39. (canceled)